Method for providing incentive, server, and non-transitory computer-readable recording medium

ABSTRACT

A system and a method allow for the provision of an incentive between different applications. A server stores information including, in association, a user identifier, a first identifier, and a second identifier received from a client terminal, and when receiving an incentive request, causes an application server to provide an incentive to the user pertaining to the first identifier corresponding to the second identifier based on the information.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. Ser. No. 17/710,155 filedMar. 31, 2022, which is a continuation of U.S. Ser. No. 14/624,976 filedFeb. 18, 2015, which claims priority to and the benefit of JapanesePatent Application No. 2014-028748 filed Feb. 18, 2014, the entirecontents of the prior applications being incorporated herein byreference.

TECHNICAL FIELD

The present disclosure relates to a method for providing an incentive, aserver, and a non-transitory computer-readable recording medium.

BACKGROUND ART

In a conventional online game system, a plurality of users participateusing client terminals. An application for online gaming is installed oneach client terminal, and the user participates in the online game usingthe application. In such a system, a mechanism for providing anincentive is adopted on the same platform (i.e. in the same online gameusing the same application; for example, see Patent Literature 1).

CITATION LIST Patent Literature

-   Patent Literature 1: JP 2013-066524 A

SUMMARY Technical Problem

In a conventional system, however, it is assumed that an incentive isprovided on the same platform, and an incentive cannot be providedbetween different platforms, i.e. between different applications.

The present disclosure has been conceived in light of the above problemand provides a method, a server, and a non-transitory computer-readablerecording medium that can provide an incentive between differentapplications.

Solution to Problem

In order to solve the above problem, a method according to the presentdisclosure is a method for a system comprising a server, a clientterminal, and an application server, the method comprising: the clientterminal transmitting a user identifier and a first identifier to theserver when a first application is launched; transmitting the useridentifier and a second identifier to the server when a secondapplication is launched; and transmitting an incentive request thatincludes the second identifier to the server when a predeterminedoperation pertaining to the second application is performed; and theserver storing information including, in association, the useridentifier, the first identifier, and the second identifier receivedfrom the client terminal; and when receiving the incentive request,causing the application server to provide an incentive to a userpertaining to the first identifier corresponding to the secondidentifier based on the information.

In the method according to the present disclosure, the user identifiermay be an identifier uniquely identifying the client terminal, the firstidentifier may be an identifier uniquely identifying a user in the firstapplication, and the second identifier may be an identifier uniquelyidentifying a user in the second application.

The method according to the present disclosure may further comprise:when receiving the incentive request, the server transmitting, to theapplication server, a request yielded by converting the secondidentifier included in the incentive request to the first identifier;and the application server providing the incentive to the userpertaining to the first identifier based on the request.

The method according to the present disclosure may further comprise:when an ad displayed in the first application is clicked, the clientterminal transmitting, to the server, notification of an ad click, thenotification including the first identifier, and installing the secondapplication on the client terminal; and the server storing an indicationof existence of the notification for each user, converting the secondidentifier included in the incentive request to the first identifierwhen receiving the incentive request, and transmitting the request tothe application server when notification pertaining to the firstidentifier exists.

The method according to the present disclosure may further comprise: theserver transmitting the request to the application server when receivingthe incentive request within a predetermined time period from thenotification.

The method according to the present disclosure may further comprise: theclient terminal transmitting friend graph information pertaining to thefirst application to the server and the server storing the friend graphinformation; the client terminal transmitting an installationnotification to the server when the second application is installed; andwhen receiving the installation notification, the server transmittingthe ad to a client terminal of a friend user based on the friend graphinformation.

The method according to the present disclosure may further comprise: theclient terminal transmitting, to the server, consent informationindicating whether consent is provided for transmission of the ad; andthe server transmitting the ad to the client terminal of the friend userbased on the consent information.

The method according to the present disclosure may further comprise: theclient terminal of the friend user transmitting, to the server, a secondinstallation notification when the second application is installed onthe client terminal of the friend user based on the ad; and whenreceiving the second installation notification, the server providing anincentive to a user that transmitted the installation notification.

A server according to the present disclosure comprises: communicationmeans for receiving a user identifier and a first identifier when afirst application is launched, receiving the user identifier and asecond identifier when a second application is launched, and receivingan incentive request that includes the second identifier when apredetermined operation pertaining to the second application isperformed; storage means for storing information including, inassociation, the user identifier, the first identifier, and the secondidentifier received from a client terminal; and control means for, whenreceiving the incentive request, causing an application server toprovide an incentive to a user pertaining to the first identifiercorresponding to the second identifier based on the information.

A non-transitory computer-readable recording medium according to thepresent disclosure stores instructions to be executed on a computerfunctioning as a server in a system comprising the server, a clientterminal, and an application server, the instructions causing thecomputer to execute the steps of: receiving a user identifier and afirst identifier when a first application is launched, receiving theuser identifier and a second identifier when a second application islaunched, and receiving an incentive request that includes the secondidentifier when a predetermined operation pertaining to the secondapplication is performed; storing information including, in association,the user identifier, the first identifier, and the second identifierreceived from the client terminal; and when receiving the incentiverequest, causing the application server to provide an incentive to auser pertaining to the first identifier corresponding to the secondidentifier based on the information.

Advantageous Effect

The method, server, and non-transitory computer-readable recordingmedium according to the present disclosure allow for the provision of anincentive between different applications.

BRIEF DESCRIPTION OF DRAWINGS

The present disclosure will be further described below with reference tothe accompanying drawings, wherein:

FIG. 1 is a block diagram of an incentive provision system according toEmbodiment 1;

FIG. 2 is an example of an ID management table;

FIG. 3 is an example of a table of ad click notifications;

FIG. 4 is a flowchart illustrating operations of the incentive provisionsystem according to Embodiment 1;

FIG. 5 is a block diagram of an incentive provision system according toEmbodiment 2;

FIG. 6 is an example of a friend graph table; and

FIG. 7 is a flowchart illustrating operations of the incentive provisionsystem according to Embodiment 2.

DESCRIPTION OF EMBODIMENTS

The following describes embodiments of the present disclosure.

Embodiment 1

FIG. 1 is a block diagram of an incentive provision system according toEmbodiment 1 of the present disclosure. The incentive provision systemaccording to Embodiment 1 of the present disclosure includes a clientterminal 1, a server 2 (distribution server 2), a first applicationserver 3, and a second application server 4, all of which are connectedover a network 5. The server 2 corresponds to the “server” of thepresent disclosure.

Overall, in the present system, a plurality of applications areinstalled on the client terminal 1. In the present embodiment, anexample is described of two applications being installed, namely a firstapplication and a second application. The first application is, forexample, a card game. The second application is, for example, a puzzlegame. Each application is a game that progresses by transmitting andreceiving information pertaining to the game by communicating with aserver. In other words, the first application and the second applicationproceed by communicating respectively with the first application server3 and the second application server 4.

The client terminal 1 is, for example, a mobile phone, a smart phone, atablet terminal, or the like, and includes a communication interface 10,a display 11, a user interface 12, and a control processor 13. It isassumed that the first application is installed in advance on the clientterminal 1. In the first application, an advertisement (ad) for thesecond application (second application ad) is displayed. The secondapplication ad is an ad that encourages installation of the secondapplication. The content of the second application ad is, for example,“Click here to install the second application! If you finish thetutorial on the second application, you'll get card X to use in thefirst application!”. Upon the user performing a selection operation suchas clicking, tapping, or the like (referred to below as a click) on thesecond application ad while the first application is running, the secondapplication is downloaded and installed on the client terminal 1.

The communication interface 10 communicates with the server 2 overeither or both of a wireless and wired connection.

The display 11 may be configured using a liquid crystal display, organicEL display, or the like. The display 11 outputs display pertaining tothe applications installed on the terminal. For example, if the firstapplication is a card game, the display 11 outputs display pertaining tothe game.

The user interface 12 is configured using buttons, a touch panel, or thelike, and receives input signals from the user. The user interface 12also transmits the input signals received from the user to the controlprocessor 13.

The control processor 13 performs a variety of control pertaining to theclient terminal 1. Specifically, based on operation of the userinterface 12 by the user, the control processor 13 launches the firstapplication installed on the terminal. Once the first application islaunched, the control processor 13 transmits a terminal ID and a firstapplication user ID to the server 2 via the communication interface 10.The terminal ID is an identifier for uniquely identifying the user ofthe client terminal 1. Specifically, the terminal ID may be an AndroidID, an ID for advertisement tracking (IDFA or IFA: Identifier forAdvertisers), a MAC address (Media Access Control Address), or the like.The first application user ID is an identifier for uniquely identifyingthe user in the first application. The terminal ID corresponds to the“user identifier” of the present disclosure, and the first applicationuser ID corresponds to the “first identifier” of the present disclosure.

After the first application is launched, the control processor 13displays the second application ad using the display 11. When the secondapplication ad is clicked by user operation of the user interface 12,the control processor 13 transmits an ad click notification to theserver 2 via the communication interface 10. The ad click notificationis information indicating that the second application ad has beenclicked by a predetermined user. The ad click notification includes thefirst application user ID pertaining to the user of the client terminal1. After transmitting the ad click notification to the server 2, thecontrol processor 13 installs the second application on the clientterminal 1.

Based on operation of the user interface 12 by the user, the controlprocessor 13 launches the second application installed on the clientterminal 1. Once the second application is launched, the controlprocessor 13 transmits the terminal ID and a second application user IDto the server 2. The second application user ID is an identifier foruniquely identifying the user in the second application. The secondapplication user ID corresponds to the “second identifier” of thepresent disclosure. The structure of the user identifier in the firstapplication differs from the structure of the user identifier in thesecond application.

The control processor 13 also determines whether a predeterminedoperation pertaining to the second application has been performed. Thepredetermined operation is determined in advance and is an operationsuch as launching the second application, finishing a tutorial on thesecond application, or the like. When the predetermined operation isperformed, the control processor 13 transmits an incentive request tothe server 2. The incentive request is information requesting theprovision of an incentive in the first application. The incentiverequest includes information pertaining to the second application userID and the predetermined operation. Note that the predeterminedoperation is not limited to the examples above and may, for example, beparticipation for the first time in a guild battle in the secondapplication. Alternatively, the predetermined operation may be giving apresent to a friend for the first time in the second application,logging into the second application with a predetermined persistencyrate, or the like.

The server 2 includes a communication interface 20, a memory 21, and acontrol processor 22.

The communication interface 20 communicates with the client terminal 1over either or both of a wireless and wired connection.

The memory 21 stores a variety of information. Specifically, the memory21 stores an ID management table 211 and a table 212 of ad clicknotifications. The ID management table 211 is a table that includes eachterminal ID, first application user ID, and second application user IDreceived from the client terminal 1. FIG. 2 illustrates an example ofthe ID management table 211. The ID management table 211 illustrated inFIG. 2 for example includes “ST001”, “A101”, and “B029” respectively asthe terminal ID, first application user ID, and second application userID. The ID management table 211 corresponds to the “informationincluding, in association, the user identifier, the first identifier,and the second identifier” of the present disclosure.

The table 212 of ad click notifications is a table including each adclick notification received from the client terminal 1. FIG. 3illustrates an example of the table 212 of ad click notifications. Thetable 212 of ad click notifications illustrated in FIG. 3 includes, inassociation with a terminal ID, an indication of existence (i.e.receipt) of an ad click notification and the time of receipt of the adclick notification (notification time). In FIG. 3 , the indication ofreceipt is set to 1 when an ad click notification has been received andto 0 when not received.

The control processor 22 controls the server 2 in a variety of ways.Specifically, upon receiving the terminal ID and the first applicationuser ID from the client terminal 1 via the communication interface 20,the control processor 22 stores the terminal ID and the firstapplication user ID in the memory 21. Furthermore, upon receiving theterminal ID and the second application user ID from the client terminal1 via the communication interface 20, the control processor 22 storesthe terminal ID and the second application user ID in the memory 21. Thecontrol processor 22 stores this information as the above-described IDmanagement table 211, storing the terminal ID, first application userID, and second application user ID in association.

When receiving an ad click notification from the client terminal 1 viathe communication interface 20, the control processor 22 storesinformation pertaining to the ad click notification in the memory 21 asthe table 212 of ad click notifications. Based on the first applicationuser ID included in the ad click notification, the control processor 22sets the indication of receipt of an ad click notification pertaining tothat first application user ID to 1. The control processor 22 alsostores the time that the ad click notification was received in the table212 of ad click notifications.

When receiving an incentive request from the client terminal 1 via thecommunication interface 20, the control processor 22 converts the secondapplication user ID included in the incentive request to the firstapplication user ID based on the ID management table 211. Next, thecontrol processor 22 determines whether an ad click notificationpertaining to the first application user ID has been received based onthe table 212 of ad click notifications. When an ad click notificationhas been received, the control processor 22 transmits, to the firstapplication server 3, the incentive request in which the secondapplication user ID has been converted to the first application user ID(converted incentive request). On the other hand, when no ad clicknotification has been received, the control processor 22 does nottransmit the converted incentive request to the first application server3.

The first application server 3 is a server for the first application andtransmits and receives a variety of information by communicating with aclient terminal 1 on which the first application is installed. The firstapplication server 3 manages a variety of information for each firstapplication user ID pertaining to the first application. For example,when the first application is a card game, the first application server3 manages the cards, items, various types of point information, and thelike possessed by the user based on the first application user ID. In acard game, there are rare cards or rare items that are difficult toobtain, and points are necessary to obtain cards or items. The firstapplication may be a native application, a web application, or a hybridapplication combining a native application with a web application. Aprogram in accordance with the type of the first application isinstalled in advance on the first application server 3.

When receiving the converted incentive request from the server 2, thefirst application server 3 provides the user with a predeterminedincentive based on the first application user ID included in theconverted incentive request and on information pertaining to apredetermined operation. For example, the first application server 3provides the user with a predetermined card or item, or with apredetermined number of points. The first application server 3 may varythe provided incentive in accordance with the content of thepredetermined operation. In other words, in the present system, whenreceiving the incentive request, the server 2 causes the firstapplication server 3 to provide an incentive to the user pertaining tothe first application user ID corresponding to the second applicationuser ID based on the ID management table 211.

The second application server 4 is a server for the second applicationand transmits and receives a variety of information by communicatingwith a client terminal 1 on which the second application is installed.The second application server 4 manages a variety of information foreach second application user ID pertaining to the second application.For example, when the second application is a puzzle game, then based onthe second application user ID, the second application server 4 managesthe various types of point information and the like possessed by theuser. The second application may be a native application, a webapplication, or a hybrid application combining a native application witha web application. A program in accordance with the type of the secondapplication is installed in advance on the second application server 4.

Next, operations for incentive provision in the incentive provisionsystem according to the present disclosure are described with referenceto the flowchart in FIG. 4 . The following describes the case of theuser whose terminal ID is ST001 operating the client terminal 1.

First, based on operation of the user interface 12 by the user, thecontrol processor 13 of the client terminal 1 launches the firstapplication installed on the terminal (step S1).

Next, the control processor 13 transmits the terminal ID (i.e. ST001)and the first application user ID (i.e. A101) to the server 2 via thecommunication interface 10 (step S2). The control processor 22 of theserver 2 stores the terminal ID and the first application user ID in thememory 21 (step S3).

Next, after the first application is launched, the control processor 13of the client terminal 1 displays the second application ad (step S4).When the second application ad is clicked or the like by user operationof the user interface 12, the control processor 13 transmits an ad clicknotification to the server 2 via the communication interface 10 (stepS5). The control processor 22 of the server 2 stores informationpertaining to the ad click notification in the memory 21 as the table212 of ad click notifications (step S6).

After transmitting the ad click notification to the server 2, thecontrol processor 13 of the client terminal 1 installs the secondapplication on the client terminal 1 (step S7). Based on operation ofthe user interface 12 by the user, the control processor 13 thenlaunches the second application installed on the client terminal 1 (stepS8). Once the second application is launched, the control processor 13transmits the terminal ID (i.e. ST001) and the second application userID (i.e. B029) to the server 2 (step S9). The control processor 22 ofthe server 2 stores the terminal ID and the second application user IDin the memory 21 (step S10).

Next, the control processor 13 determines whether a predeterminedoperation pertaining to the second application has been executed (stepS11), and when the predetermined operation has been executed, thecontrol processor 13 transmits an incentive request to the server 2(step S12). When receiving the incentive request from the clientterminal 1 via

the communication interface 20, the control processor 22 of the server 2converts the second application user ID included in the incentiverequest (i.e. B029) to the first application user ID (i.e. A101) basedon the ID management table 211 (step S13). Next, the control processor22 determines whether an ad click notification pertaining to the firstapplication user ID has been received based on the table 212 of ad clicknotifications (step S14). When an ad click notification pertaining tothe first application user ID has been received (step S14: yes), thecontrol processor 22 transmits the converted incentive request to thefirst application server 3 (step S15). Specifically, for user A101, thecontrol processor 22 determines whether an ad click notification hasbeen received based on the table 212 of ad click notifications in FIG. 3. When receiving the converted incentive request from the server 2, thefirst application server 3 provides the user with a predeterminedincentive based on the first application user ID included in theconverted incentive request (i.e. A101) and on a predetermined operation(step S16).

In the incentive provision system according to Embodiment 1, the clientterminal 1 transmits the terminal ID and the application ID to theserver 2 upon launching of each application, and the server 2 stores theterminal ID, the first application user ID, and the second applicationuser ID in association. Therefore, this system allows for incentiveprovision between different applications. Since the second applicationad displayed in the first application leads to incentive provision inthe first application, the second application ad is enticing for theuser and has a strong advertising affect. The incentive provision systemaccording to the present embodiment can thus increase the advertisingeffect of an ad for an application displayed in another application.

When the first application is launched, and the control processor 13 ofthe client terminal 1 transmits the terminal ID to the server 2 via thecommunication interface 10 (step S2 in FIG. 4 ), the number of terminalIDs transmitted may be two or more. For example, the control processor13 may transmit both an ID for advertisement tracking and a MAC addressto the server 2. With this approach, even if one of the terminal IDsbecomes unusable, the other terminal ID may be used as a key for thepresent system to operate.

Similarly, when the second application is launched, and the controlprocessor 13 of the client terminal 1 transmits the terminal ID to theserver 2 via the communication interface 10 (step S9 in FIG. 4 ), thenumber of terminal IDs transmitted may be two or more. For example, thecontrol processor 13 may transmit both an ID for advertisement trackingand a MAC address to the server 2. With this approach, even if one ofthe terminal IDs becomes unusable, the other terminal ID may be used asa key for the present system to operate.

In the present system, the only condition for transmitting the convertedincentive request in step S14 is whether an ad click notification hasbeen received. Additionally, the notification time of the ad clicknotification may also be used as a condition. For example, the controlprocessor 22 may transmit the converted incentive request to the firstapplication server 3 when the time that the incentive request isreceived is within a predetermined time period from the notificationtime of the ad click notification (for example, within 24 hours).Furthermore, in the determination in step S14, the control processor 22may transmit the converted incentive request to the first applicationserver 3 even when no ad click notification has been received. With thisconfiguration, an incentive is also provided to a user that has notinstalled the second application by clicking on the second applicationad. In the present system, the client terminal 1 transmits the terminal

ID and the first application user ID to the server 2, yet the presentdisclosure is not limited in this way. Alternatively, the firstapplication server 3 may transmit the terminal ID and the firstapplication user ID to the server 2. In this case, the first applicationserver 3 detects the launching of the first application on the clientterminal 1 by communicating with the client terminal 1 and transmits theterminal ID pertaining to the client terminal 1 and the firstapplication user ID to the server 2. Similarly, the client terminal 1transmits the ad click notification to the server 2 in the exampleabove, yet the present disclosure is not limited in this way.Alternatively, the first application server 3 may transmit the ad clicknotification to the server 2.

Similarly, in the present system, the client terminal 1 transmits theterminal ID and the second application user ID to the server 2, yet thepresent disclosure is not limited in this way. Alternatively, the secondapplication server 4 may transmit the terminal ID and the secondapplication user ID to the server 2. In this case, the secondapplication server 4 detects the launching of the second application onthe client terminal 1 by communicating with the client terminal 1 andtransmits the terminal ID pertaining to the client terminal 1 and thesecond application user ID to the server 2. Similarly, the clientterminal 1 transmits the incentive request to the server 2 in theexample above, yet the present disclosure is not limited in this way.Alternatively, the second application server 4 may transmit theincentive request to the server 2.

Embodiment 2

The following describes Embodiment 2 of the present disclosure. FIG. 5is a block diagram illustrating the structure of an incentive provisionsystem according to Embodiment 2 of the present disclosure. The samereference signs are provided for the same components as in Embodiment 1,and a description thereof is omitted. The incentive provision systemaccording to Embodiment 2 differs from the structure of Embodiment 1 inthat a friend graph pertaining to the first application is used, and inthat operations pertaining to ad distribution for the second applicationad differ.

In the incentive provision system according to Embodiment 2, a friendgraph indicating the relationship between users is used in the firstapplication. The first application provided by the first applicationserver 3 is preferably an application pertaining to a social networkingservice (SNS). In the first application, when two users register eachother as friends, they become friend users. The friend graph isinformation pertaining to friend users. The relationship between usersindicated in the friend graph is not limited to the relationship betweenusers that have performed friend registration and may be therelationship between users according to the group to which users belongin the game, such as a team, guild, country, or the like. In the presentembodiment, in addition to the other user with whom a user has mutuallyperformed friend registration, users belonging to the same group arealso referred to as friend users.

Once the first application is launched, the control processor 13 of theclient terminal 1 according to Embodiment 2 transmits the terminal IDand the first application user ID to the server 2 via the communicationinterface 10. Furthermore, the control processor 13 transmitsinformation on the friend graph pertaining to the first application(friend graph information) to the server 2. Specifically, when a friendis added, changed, deleted, or the like in the first application, thecontrol processor 13 transmits information including the firstapplication user ID of the added, changed, or deleted friend and theuser's own first application user ID to the server 2.

The control processor 13 also installs the second application on theclient terminal 1. Installation of the second application may be inresponse to a click on the second application ad, as in Embodiment 1.Alternatively, the second application may be downloaded and installed bythe user searching on a predetermined site.

After the second application is installed on the client terminal 1,based on operation of the user interface 12 by the user, the controlprocessor 13 launches the second application. Once the secondapplication is launched, the control processor 13 transmits the terminalID and a second application user ID to the server 2. Furthermore, thecontrol processor 13 transmits a notification that the secondapplication has been installed on the client terminal 1 (installationnotification) to the server 2. The second application user ID isincluded in the installation notification.

In addition to the ID management table 211 and the table 212 of ad clicknotifications, the memory 21 of the server 2 according to Embodiment 2stores a friend graph table 213. The friend graph table 213 is a tablebased on the friend graph information received from the client terminal1. FIG. 6 illustrates an example of the friend graph table 213. Thefriend graph table 213 includes first application user IDs andinformation on the friend users for each first application user ID. Forexample, for the user whose first application user ID is A101, the userswhose first application user IDs are A103, A121, and A157 are stored asfriend users.

When receiving the friend graph information from the client terminal 1,the control processor 22 of the server 2 according to Embodiment 2 edits(adds, changes, and deletes) the friend graph table 213 in the memory 21based on the first application user IDs included in the friend graphinformation.

Furthermore, when receiving an installation notification from the clientterminal 1, the control processor 22 converts the second applicationuser ID included in the installation notification to the firstapplication user ID based on the ID management table 211. Next, thecontrol processor 22 retrieves the first application user ID of eachfriend user pertaining to the first application user ID based on thefriend graph table 213. Via the communication interface 20, the controlprocessor 22 then distributes (transmits) the second application ad tothe client terminal of each user corresponding to the retrieved firstapplication user IDs of friend users. On the client terminal 1 b thatreceives the second application ad, the second application ad isdisplayed when the first application is launched. The content of thesecond application ad is, for example, “Click here to install the secondapplication that user X is also using! If you finish the tutorial on thesecond application, you'll get card X to use in the first application!”.

Next, operations for ad distribution in the incentive provision systemaccording to the present disclosure are described with reference to theflowchart in FIG. 7 . The following describes the case of the user whoseterminal ID is ST001 operating the client terminal 1.

First, based on operation of the user interface 12 by the user, thecontrol processor 13 of the client terminal 1 launches the firstapplication installed on the terminal (step S101).

Next, the control processor 13 transmits the terminal ID (i.e. ST001)and the first application user ID (i.e. A101) to the server 2 via thecommunication interface 10 (step S102). The control processor 22 of theserver 2 stores the terminal ID and the first application user ID in thememory 21 (step S103).

The control processor 13 transmits friend graph information pertainingto the first application to the server 2 (step S104). For example, whena user (such as first application user ID A167) is added as a frienduser after the friend graph information has been transmitted to theserver 2 in the past, the control processor 13 transmits friend graphinformation including the first application user IDs A101 and A167 tothe server 2. The control processor 22 of the server 2 stores the friendgraph information in the memory 21. Specifically, the control processor22 updates the friend graph table 213 of the memory 21 (step S105). Forexample, based on the first application user IDs A101 and A167 includedin the friend graph information, the control processor 22 adds A167 as afriend user for first application user ID A101.

Next, the client terminal 1 installs the second application on theclient terminal 1 (step S106). Based on operation of the user interface12 by the user, the control processor 13 then launches the secondapplication installed on the client terminal 1 (step S107). Once thesecond application is launched, the control processor 13 transmits theterminal ID (i.e. ST001) and the second application user ID (i.e. B029)to the server 2 (step S108). The control processor 22 of the server 2stores the terminal ID and the second application user ID in the memory21 (step S109).

Furthermore, the control processor 13 transmits the installationnotification to the server 2 (step S110). When receiving theinstallation notification from the client terminal 1, the controlprocessor 22 of the server 2 converts the second application user IDincluded in the installation notification to the first application userID based on the ID management table 211 (step S111). Next, the controlprocessor 22 retrieves the first application user ID of each friend userpertaining to the first application user ID based on the friend graphtable 213. For example, the control processor 22 retrieves the firstapplication user IDs A103, A121, and A157 as friend users of A101. Viathe communication interface 20, the control processor 22 thendistributes the second application ad to the client terminal 1 b of eachuser corresponding to the retrieved first application user IDs of friendusers (step S112). On the client terminal 1 b that receives the secondapplication ad, the ad is displayed when the first application islaunched (step S113). The content of the second application ad is, forexample, “Click here to install the second application that user X isalso using! If you finish the tutorial on the second application, you'llget card X to use in the first application!”. User X corresponds to theuser name or the like of the user whose first application user ID isA101. Operations pertaining to incentive provision after display of thead are the same as the operations in FIG. 4 (steps S1 to S16).

In the incentive provision system according to Embodiment 2, the server2 thus distributes the second application ad to friend users based onthe friend graph of the first application. Via the second applicationad, an incentive is provided between different applications. In thesystem according to Embodiment 2, a word-of-mouth effect between userscan be expected since ads are distributed using the friend graph, thusincreasing the advertising effect of an ad for an application displayedin another application.

The control processor 13 of the client terminal 1 may be configured totransmit in advance, to the server 2, consent information indicatingwhether to transmit the ad to the friend user. In this case, based onthe consent information, the control processor 22 of the server 2distributes the ad to the friend users in step S112 when consent for addistribution is provided yet does not distribute the ad when consent isnot provided. The consent information may be set for all friend userscollectively or for each friend user separately. In other words, it ispossible to allow one friend user to consent to ad distribution andanother friend user to refuse ad distribution. With this approach, whena user does not wish to distribute ads to friend users, distribution canbe suspended, thereby protecting the user's privacy.

On the client terminal 1 b to which the second application ad has beendistributed, when the second application ad is clicked by the user andthe second application is installed, the control processor 22 of theserver 2 may receive an installation notification (second installationnotification) from the client terminal 1 b. In this case, the secondapplication ad is distributed to the friend users of the user of theclient terminal 1 b. In other words, with this structure, ads aredistributed all the way to friend users of friend users. This approachallows for the second application ad to be distributed by word of mouthover a wider range based on friend lists.

Furthermore, when receiving the second installation notification, thecontrol processor 22 of the server 2 may be configured to provide apredetermined incentive to the client terminal (client terminal 1 inFIG. 7 ) of the user who served as the occasion for distributing thesecond application ad to the client terminal 1 b (notifying user). Whenadopting this structure, the first application user ID of the notifyinguser is included in the second application ad, and the first applicationuser ID included in the second application ad is included in the secondinstallation notification. In this way, the first application user ID ofthe notifying user is transmitted and received between the clientterminal 1 b and the server 2. Based on the first application user IDincluded in the second installation notification, the control processor22 of the server 2 provides a predetermined incentive to the notifyinguser. With this approach, the notifying user is motivated to distributethe ad, thus encouraging broader ad distribution. When a plurality ofnotifying users serve as the occasion for distributing the secondapplication ad to the client terminal 1 b of a certain friend user, thecontrol processor 22 of the server 2 may, when receiving the secondinstallation notification, provide the predetermined incentive to all ofthe notifying users.

In the present system, the client terminal 1 transmits the terminal IDand the first application user ID to the server 2, yet the presentdisclosure is not limited in this way. Alternatively, the firstapplication server 3 may transmit the terminal ID and the firstapplication user ID to the server 2. In this case, the first applicationserver 3 detects the launching of the first application on the clientterminal 1 by communicating with the client terminal 1 and transmits theterminal ID pertaining to the client terminal 1 and the firstapplication user ID to the server 2. Similarly, the client terminal 1transmits the friend graph information to the server 2 in the exampleabove, yet the present disclosure is not limited in this way.Alternatively, the first application server 3 may transmit the friendgraph information to the server 2.

Similarly, in the present system, the client terminal 1 transmits theterminal ID and the second application user ID to the server 2, yet thepresent disclosure is not limited in this way. Alternatively, the secondapplication server 4 may transmit the terminal ID and the secondapplication user ID to the server 2. In this case, the secondapplication server 4 detects the launching of the second application onthe client terminal 1 by communicating with the client terminal 1 andtransmits the terminal ID pertaining to the client terminal 1 and thesecond application user ID to the server 2. Similarly, the clientterminal 1 transmits the installation notification to the server 2 inthe example above, yet the present disclosure is not limited in thisway. Alternatively, the second application server 4 may transmit theinstallation notification to the server 2. Similarly, the clientterminal 1 b transmits the second installation notification to theserver 2 in the example above, yet the present disclosure is not limitedin this way. Alternatively, the second application server 4 may transmitthe second installation notification to the server 2.

A computer is preferably used to function as the client terminal 1 orthe server 2. A program containing the processing for achieving thefunctions of the client terminal 1 or the server 2 is stored in thememory of the computer, and the functions are achieved by the centralprocessing unit (CPU) of the computer reading and executing the program.

Although the present disclosure has been described based on drawings andexamples, it is to be noted that various changes and modifications willbe apparent to those skilled in the art based on the present disclosure.Therefore, such changes and modifications are to be understood asincluded within the scope of the present disclosure. For example, thefunctions and the like included in the various means and steps may bereordered in any logically consistent way. Furthermore, means or stepsmay be combined into one or divided.

1. A method comprising: receiving a first digital benefit requestincluding a second app user identifier of a first user, that identifiesthe first user in a second application, when a predetermined operationpertaining to the second application is performed, the first digitalbenefit request being information requesting provision of a digitalbenefit in a first application; and based on the first digital benefitrequest, causing provision of the digital benefit in the firstapplication to the first user by determining the first user based on afirst app user identifier of the first user, that identifies the firstuser in the first application, corresponding to the second app useridentifier of the first user.
 2. The method of claim 1, furthercomprising storing, in a memory, association information that associateswith each other the first app user identifier, the second app useridentifier, and a first user identifier identifying the first user,wherein the digital benefit is caused to be provided based on referenceto the stored association information.
 3. The method of claim 1, furthercomprising receiving a notification of information related to a click ofa link for installation of the second application, the link beingdisplayed in the first application, and the notification including thefirst app user identifier; and causing the second application to beinstalled in response to receiving the notification.
 4. The method ofclaim 3, wherein the digital benefit is caused to be provided inresponse to receiving the first digital benefit request within apredetermined time period from receipt of the notification.
 5. Themethod of claim 1, wherein the digital benefit is for use in only thefirst application.
 6. The method of claim 1, further comprisingreceiving a second digital benefit request including the second app useridentifier of a second user, that identifies the second user in thesecond application, when the predetermined operation pertaining to thesecond application is performed, the second user having a predeterminedrelationship with the first user; and based on the second digitalbenefit request, causing provision of the digital benefit in the firstapplication to the second user by determining the second user based onthe first app user identifier of the second user, that identifies thesecond user in the first application, corresponding to the second appuser identifier of the second user.
 7. The method of claim 1, furthercomprising transmitting second application information to a second userhaving a predetermined relationship with the first user, based on thepredetermined operation.
 8. A system comprising: circuitry configured toreceive a first digital benefit request including a second app useridentifier of a first user, that identifies the first user in a secondapplication, when a predetermined operation pertaining to the secondapplication is performed, the first digital benefit request beinginformation requesting provision of a digital benefit in a firstapplication; and based on the first digital benefit request, causeprovision of the digital benefit in the first application to the firstuser by determining the first user based on a first app user identifierof the first user, that identifies the first user in the firstapplication, corresponding to the second app user identifier of thefirst user.
 9. The system of claim 8, wherein the circuitry is furtherconfigured to store, in a memory, association information thatassociates with each other the first app user identifier, the second appuser identifier, and a first user identifier identifying the first user,and the digital benefit is caused to be provided based on reference tothe stored association information.
 10. The system of claim 8, whereinthe circuitry is further configured to receive a notification ofinformation related to a click of a link for installation of the secondapplication, the link being displayed in the first application, and thenotification including the first app user identifier; and cause thesecond application to be installed in response to receiving thenotification.
 11. The system of claim 10, wherein the digital benefit iscaused to be provided in response to receiving the first digital benefitrequest within a predetermined time period from receipt of thenotification.
 12. The system of claim 8, wherein the digital benefit isfor use in only the first application.
 13. The system of claim 8,wherein the circuitry is further configured to receive a second digitalbenefit request including the second app user identifier of a seconduser, that identifies the second user in the second application, whenthe predetermined operation pertaining to the second application isperformed, the second user having a predetermined relationship with thefirst user; and based on the second digital benefit request, causeprovision of the digital benefit in the first application to the seconduser by determining the second user based on the first app useridentifier of the second user, that identifies the second user in thefirst application, corresponding to the second app user identifier ofthe second user.
 14. The system of claim 8, wherein the circuitry isfurther configured to transmit second application information to asecond user having a predetermined relationship with the first user,based on the predetermined operation.
 15. A non-transitorycomputer-readable medium storing thereon computer program instructionscausing a system to execute: receiving a first digital benefit requestincluding a second app user identifier of a first user, that identifiesthe first user in a second application, when a predetermined operationpertaining to the second application is performed, the first digitalbenefit request being information requesting provision of a digitalbenefit in a first application; and based on the first digital benefitrequest, causing provision of the digital benefit in the firstapplication to the first user by determining the first user based on afirst app user identifier of the first user, that identifies the firstuser in the first application, corresponding to the second app useridentifier of the first user.
 16. The non-transitory computer-readablemedium of claim 15, wherein the computer program instructions furthercause the system to execute storing, in a memory, associationinformation that associates with each other the first app useridentifier, the second app user identifier, and a first user identifieridentifying the first user, wherein the digital benefit is caused to beprovided based on reference to the stored association information. 17.The non-transitory computer-readable medium of claim 15, wherein thecomputer program instructions further cause the system to executereceiving a notification of information related to a click of a link forinstallation of the second application, the link being displayed in thefirst application, and the notification including the first app useridentifier; and causing the second application to be installed inresponse to receiving the notification.
 18. The non-transitorycomputer-readable medium of claim 17, wherein the digital benefit iscaused to be provided in response to receiving the first digital benefitrequest within a predetermined time period from receipt of thenotification.
 19. The non-transitory computer-readable medium of claim15, wherein the digital benefit is for use in only the firstapplication.
 20. The non-transitory computer-readable medium of claim15, wherein the computer program instructions further cause the systemto execute receiving a second digital benefit request including thesecond app user identifier of a second user, that identifies the seconduser in the second application, when the predetermined operationpertaining to the second application is performed, the second userhaving a predetermined relationship with the first user; and based onthe second digital benefit request, causing provision of the digitalbenefit in the first application to the second user by determining thesecond user based on the first app user identifier of the second user,that identifies the second user in the first application, correspondingto the second app user identifier of the second user.